@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@francoisl We have another error which reproducible only for native platforms. The problem becomes from here.
On IOS the Url.getPathFromURL function gets file:///Users/... as param and returns Users/... which causes the download to fail here.
And on Android It does not work at all. It gets data/user/0/com.expensify.chat.dev/... and returns '' which causes the download to fail here.

Here we should use original status.uri for IOS and file://${status.uri} for Android instead sourceURI.

@francoisl, I don't have access to this doc, but according to the discussion here, besides adding a Ready To Build label you have to manually start the build

https://stackoverflowteams.com/c/expensify/questions/15778/15779

Yes I did, it just takes a while to build :) Anyway, it's built now except for iOSdesktop, I'll restart it manually.

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/37122/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/37122/index.html
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/37122/NewExpensify.dmg	https://37122.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

At step 4 of the test, what gets downloaded for me is just a HTML page, is this due to the same issue you were referring to in this comment?

I'm seeing "Attachment cannot be downloaded" error on iOS (simulator)

Weirdly, on a physical device even with current prod (without the fix from this PR), video preview is not displayed. Was this discussed and is this by design?

Also, could you please upload the missing videos for iOS/Android (native)?

video preview is not displayed. Was this discussed and is this by design?

Yes, at the moment on production, videos are still treated as regular file attachments. We just deployed the video player feature to staging.

Yes, at the moment on production, videos are still treated as regular file attachments. We just deployed the video player feature to staging

Ah, I see, thank you @francoisl!

The "Attachment cannot be downloaded" error is still present on a physical device

@eVoloshchak @francoisl didn't you notice my comment ?

Ah, I see now!
Let's fix those two issues too, we definitely should get the whole download flow working

Ah, I see now! Let's fix those two issues too, we definitely should get the whole download flow working

@eVoloshchak It seems this PR will fix the problem with urls. We need hold current PR on that one

That PR you linked is merged. I tested again and pulled main into your branch locally, by default the proposed filename for download doesn't have an extension, do you see a way to fix that?

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/37122/index.html	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/37122/NewExpensify.dmg	https://37122.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

That PR you linked is merged. I tested again and pulled main into your branch locally, by default the proposed filename for download doesn't have an extension, do you see a way to fix that?

Currently no. This needs to be explored further . But if it's a bug, it should be fixed in that PR because it was opened specifically to fix uploaded files.

@eVoloshchak can you complete the checklist please?

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified tests pass on all platforms & I tested again on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: mWeb Chrome

MacOS: Chrome / Safari

MacOS: Desktop

🚀 Deployed to staging by https://github.com/francoisl in version: 1.4.47-0 🚀

🚀 Deployed to production by https://github.com/roryabraham in version: 1.4.47-10 🚀